| Senden Sie eine E-Mail an
creator |
Reimann, Peter
| date |
2007-08-31
| | | description |
107 pages
| |
The concept of the Service Oriented Architecture describes an
abstract mechanism to model business processes in an efficient way
based on loosely coupled services. There are two different points of
view for modeling business processes. The orchestration defines the
process and the logical sequence of the services from the
perspective of one single participant. Beside this local aspect, in
a choreography we have a global view on all participants and the
interactions between them as well as their interaction behavior (e.
g. control flow and data dependencies).
In the Web Service Environment the most accepted standard to
describe orchestrations is WS-BPEL (or BPEL for short), which has
been developed by the Organization for the Advancement of Structured
Information Standards (OASIS). It distinguishes between Executable
and Abstract Processes. Executable Processes contain all necessary
information to execute them (e. g. in a workflow engine), while some
information concerning the execution may be hidden in an Abstract
Process. As choreography description languages there exist several
different approaches. One of them is the BPEL extension BPEL4Chor,
which has been developed in a cooperation of the Institute of
Architecture of Application Systems at the University of Stuttgart
and the Hasso-Plattner-Institute at the University of Potsdam.
Having given one of the two descriptions for a business process, it
could be beneficial to transform it into the other one. Transforming
the separate BPEL processes into one BPEL4Chor choreography gives us
a global view of the interaction between the participants and helps
us to analyze and optimize this interaction. The other direction can
be used to convert the global and abstract business process
description into executable processes and thus provides an
implementation of the process.
This work deals with the transformation from BPEL4Chor to BPEL
Abstract Processes. It can be seen as a step in the transformation
of a business process description into an implementation of the
business process.
| format |
application/pdf
| | 1267923 Bytes | |